Automated information retrieval based on supplier risk

ABSTRACT

Techniques are provided for automated information retrieval based on supplier risk. In an embodiment, a selection of a supplier identifier value that identifies a supplier during a supplier onboarding process in an e-procurement system is received. A digital data repository of the e-procurement system is queried to seek a data record matching the selected supplier identifier value. In response to determining that the data repository has a record matching the selected supplier identifier value, a risk score value associated with the selected supplier identifier value is identified from a dataset of risk score values that is stored in the data repository. A unique mapping table is generated that maps each supplier risk score value of one or more supplier risk score values to one or more information request identifiers, the one or more supplier risk score values including the risk score value associated with the selected supplier identifier value. A custom digital data entry form is generated that comprises one or more information request fields that are mapped to the risk score value associated with the selected supplier identifier value. The custom data entry form is transmitted to a computer associated with the supplier corresponding to the selected supplier identifier value, the custom data form prompting the supplier to take action, respond, or contribute information back to the server computer.

FIELD OF THE DISCLOSURE

One technical field of the present disclosure is computer-implementedsoftware systems that support digital procurement functions. Anothertechnical field is computer-implemented graphical user interfaces,including linking forms or webpages of a computer-implementedapplication and automatically modifying workflows of programmedapplications.

BACKGROUND

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

The operation of server computers and computer application programsadapted to provide electronic digital procurement (e-procurement) andspend management functions has been hampered in the past by inefficientprocesses to achieve entry of supplier information that is essential tocomplete a digital transaction. For example, a buyer associated with anenterprise, who is seeking to buy goods from a supplier and wishes tocreate a purchase order or requisition for the goods in an e-procurementsystem, may be unable to complete this operation if the supplier has notpreviously entered or confirmed the entry of data describing thesupplier and its payment processes.

Supplier information necessary to create a complete supplier informationmanagement (SIM) record in an e-procurement system or ERP systemincludes more than just name and address. Examples include data relatingto international compliance, banking details, tax details, status undervarious legal schemes such as whether the supplier is a women-ownedbusiness, and so forth. This data must be entered for all new suppliersand also maintained over time.

This data, data relating to past transactions where a particularsupplier was involved, and data about the particular supplier retrievedfrom third party sources can be used to compute supplier health and riskscore values. Supplier risk scores can represent a risk that thesupplier will default on a supply transaction. Once a prospective buyerunderstands a general assessment of the risk associated with a supplier,a buyer wants to know specific things about the supplier in order toinitiate a transaction.

In the past, this problem has been addressed by requiring the buyer, orother personnel associated with the buying enterprise, to draft and sende-mail messages, make telephone calls or initiate other manualcommunications to the supplier, in which the supplier is requested toconnect to the e-procurement system and provide the necessary data. Thisapproach is inefficient and error-prone.

Based on the foregoing, there is a need to automate the exchange ofuseful data between a buyer and supplier of a prospective transaction toimprove the efficiency and accuracy of e-procurement transactions. Thetechniques described herein address these issues.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example networked computer system in which variousembodiments may be practiced.

FIG. 2 illustrates a unique mapping table that maps supplier risk scorevalues to information request identifiers.

FIG. 3 illustrates a unique mapping table that maps risk score componentvalues to information request identifiers.

FIG. 4 illustrates an example process of providing automated informationrequests based on supplier risk analysis, according to variousembodiments.

FIG. 5 illustrates an example graphical user interface (GUI) of adigital display device, which may be generated under program controlusing the techniques herein for selecting a type of form for onboardinga supplier.

FIG. 6 illustrates an example GUI of a new supplier request form.

FIG. 7 illustrates an example GUI for searching and selecting a supplierduring a supplier onboarding process.

FIG. 8 illustrates an example GUI for displaying risk score data andsupplier details during a supplier onboarding process.

FIG. 9 illustrates an example GUI for displaying risk score data of aparticular supplier entity to a buyer.

FIG. 10 illustrates an example GUI for a basic data entry form prompt inemail format.

FIG. 11 illustrates a computer system upon which an embodiment of theinvention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form to avoid unnecessarily obscuring the presentinvention.

Embodiments are described in sections according to the followingoutline:

-   -   1.0 GENERAL OVERVIEW    -   2.0 EXAMPLE NETWORKED COMPUTER SYSTEM    -   3.0 METHOD OVERVIEW    -   4.0 IMPLEMENTATION EXAMPLE—HARDWARE OVERVIEW    -   5.0 OTHER ASPECTS OF DISCLOSURE

1.0 GENERAL OVERVIEW

In various embodiments, methods and computer systems are provided thatare programmed or configured to enable improved workflow and computingefficiency by using intelligent mappings and automated data formgeneration to systematize information retrieval based on supplier riskassessments. Previous approaches required manual participation of buyeragents to retrieve data regarding questions relating to supplier risk,resulting in inefficient and error prone workflows. However, the presentapproach uses map risk score values to information request identifiersand automatically generate and transmit custom data forms to suppliers,thereby decreasing the need for buyer agents to unnecessarily manuallyinteract with suppliers through an e-procurement system and thusimproving overall e-procurement computing system efficiency.

In an embodiment, a computer implemented method comprises a selection ofa supplier identifier value that identifies a supplier during a supplieronboarding process in an e-procurement system is received. A digitaldata repository of the e-procurement system is queried to seek a datarecord matching the selected supplier identifier value. In response todetermining that the data repository has a record matching the selectedsupplier identifier value, a risk score value associated with theselected supplier identifier value is identified from a dataset of riskscore values that is stored in the data repository. A unique mappingtable is generated that maps each supplier risk score value of one ormore supplier risk score values to one or more information requestidentifiers, the one or more supplier risk score values including therisk score value associated with the selected supplier identifier value.A custom digital data entry form is generated that comprises one or moreinformation request fields that are mapped to the risk score valueassociated with the selected supplier identifier value. The custom dataentry form is transmitted to a computer associated with the suppliercorresponding to the selected supplier identifier value, the custom dataform prompting the supplier to take action, respond, or contributeinformation back to the server computer.

In another embodiment, a computer implemented method comprises aselection of a supplier identifier value that identifies an existingsupplier in an e-procurement system is received. A digital datarepository of the e-procurement system is queried to identify a riskscore value associated with the selected supplier identifier value froma dataset of risk score values that is stored in the data repository. Aunique mapping table is generated that maps each supplier risk scorevalue of one or more supplier risk score values to one or moreinformation request identifiers, the one or more supplier risk scorevalues including the risk score value associated with the selectedsupplier identifier value. A custom digital data entry form is generatedthat comprises one or more information request fields that are mapped tothe risk score value associated with the selected supplier identifiervalue. The custom data entry form is transmitted to a computerassociated with the supplier corresponding to the selected supplieridentifier value, the custom data form prompting the supplier to takeaction, respond, or contribute information back to the server computer.

In various embodiments, a supplier risk score value represents a riskthat the supplier will default on a supply transaction and is calculatedbased on a plurality of data items that represent historic performanceof the supplier. The supplier risk score value may represent a risk thatthe supplier will default on a supply transaction and is calculatedbased on a financial score value, a judicial score value, and a newssentiment score value. In an embodiment, the financial score valuerepresents a rating of the supplier based upon financial indicators suchas a third-party credit rating score value, a count of previous latepayments, and/or a representation of whether the supplier has everentered bankruptcy. In an embodiment, a judicial score value is basedupon publicly available legal status databases and represents a numberof lawsuits filed against the supplier, such as collections actions. Inan embodiment, the news sentiment score value represents a sentimentvalue calculated by third-party sentiment calculation services basedupon sentiments expressed in social media postings about the supplier.For example, the supplier may maintain a page in a third-party socialnetworking site and customers may post comments on the page; third-partysentiment analysis software systems are called, using programmatic callsto APIs or the like, to retrieve data indicating the aggregate sentimentof such comments.

In various embodiments, the computer implemented methods may furthercomprise, in response to determining that the digital data repositorydoes not include a record matching the selected supplier identifier,generating a risk score value for the selected supplier identifier andstoring the risk score value in a new record in the digital datarepository that matches the selected supplier identifier. The computerimplemented methods may further comprise generating a unique mapping ofeach financial score value, judicial score value, and news sentimentscore value to one or more information request identifiers, thefinancial score value, judicial score value, and news sentiment scorevalue associated with the selected supplier.

2.0 EXAMPLE NETWORKED COMPUTER SYSTEM

FIG. 1 is a block diagram of an example computer network system in whichvarious embodiments may be practiced. FIG. 1 is shown in simplified,schematic format for purposes of illustrating a clear example and otherembodiments may include other elements.

In an embodiment, a networked computer system 100 comprises a servercomputer (“server” for short) 102, buyer computer 118, supplier computer120, an external data source 116, which are communicatively coupleddirectly or indirectly via network 114.

In an embodiment, the server computer 102 executes Mapping GeneratingInstructions 104 and Data Form Generating Instructions 106, thefunctions of which are described in other sections herein. The server102 may also execute additional code, such as code for an E-ProcurementSystem 108. Although the Mapping Generating Instructions 104 and DataForm Generating Instructions 106 are shown in FIG. 1 as executing on theserver 102 separately from the E-Procurement System 108, the MappingGenerating Instructions 104 and Data Form Generating Instructions 106may be a part of computer instructions installed as part of theE-Procurement System 108, as a module or a plug-in to supplementfeatures of the E-Procurement System 108, as a separate instance ofexecuting code on the server 102 than an instance of code of theE-Procurement System 108, or any other arrangement depending on theneeds of a buyer entity.

The E-Procurement System 108 may include digital data repositories suchas a Transactional Database 110 managed by the E-Procurement System 108.The Transactional Database 110 may include transactional information onone or more supplier entities as well associated details on the supplierentities. The Transactional Database 110 may also include, for eachsupplier entity, one or more records of orders or transactions betweenthe buyer entity and a respective supplier entity along with risk scorevalues associated with each supplier entity.

The E-Procurement System 108 may include a Mapping Database 112 managedby the E-Procurement System 108. The Mapping Database 112 may includemapping information that maps supplier risk score values to informationrequest identifiers.

Although the Transactional Database 110 and Mapping Database 112 areshown in FIG. 1 as encompassed by the E-Procurement System 108, theTransactional Database 110 and Mapping Database 112 may exist separatelyfrom the E-Procurement System 108 and/or server 102, and may be accessedvia network 114.

Additional computing elements, code or other functional elements thatare not shown in FIG. 1 may be provided by the procure E-ProcurementSystem 108.

The server 102 is accessible over a network 114 by multiple computingdevices, such as Supplier Computer 120, and Buyer Computer 118. Anyother number of supplier or buyer computers may be registered with theserver 102 at any given time. Thus, the elements in FIG. 1 are intendedto represent one workable embodiment but are not intended to constrainor limit the number of elements that could be used in other embodiments.

Server computer 102 may be implemented using a server-class computer orother computers having one or more processor cores, co-processors, orother computers. Server computer 102 may be a physical server computerand/or a virtual server instance stored in a data center, such asthrough cloud computing. The server computer 102 may be programmed orconfigured to store transaction data and analyze the transaction data inorder to generate recommendations. The server computer may comprise aplurality of communicatively coupled server computers including a servercomputer for storing past transaction data 104. The server computer 102may additionally receive information that is not specific to individualtransactions, such as public contact information of suppliers, websiteURLs for suppliers, and catalogue information for suppliers.

The External Data Source 116 may be accessed via network 114 by theserver 102. The External Data Source 116 may include informationrelating to one or more supplier entities as well associated details onthe supplier entities. The data from the External Data Source 116 may beused as input to any of the Mapping Generating Instructions 104, DataForm Generating Instructions 106, and E-Procurement System 108. Althoughthere is one External Data Source 116 shown in FIG. 1, any other numberof External Data Sources 116 may be accessed by the server at any giventime.

The Mapping Generating Instructions 104 may be programmed or configuredto generate mappings that associate risk score values of a supplier withinformation request identifiers. For example, the Mapping GeneratingInstructions 104 may include features to access information from theTransactional Database 110 and Mapping Database 112 managed by theE-Procurement System 108. The Mapping Generating Instructions 104 mayalso access the External Data Source 116 and transmit or receive data toand from the Data Form Generating Instructions 106 and E-ProcurementSystem 108. The Mapping Generating Instructions 106 may also be used forimplementing aspects of the flow diagrams that are further describedherein.

The Data Form Generating Instructions 106 may be programmed orconfigured to generate custom digital data entry forms (“forms”). Forexample, the Data Form Generating Instructions 106 may include featuresto access information from the Transactional Database 110 and MappingDatabase 112 managed by the E-Procurement system 108. The Data FormGenerating Instructions 106 may also access the External Data Source 116and transmit or receive data to and from the Mapping GeneratingInstructions 104 and E-Procurement System 108. The Data Form GeneratingInstructions 106 may also be used for implementing aspects of the flowdiagrams that are further described herein.

Computer executable instructions described herein may be in machineexecutable code in the instruction set of a CPU and may have beencompiled based upon source code written in JAVA, C, C++, OBJECTIVE-C, orany other human-readable programming language or environment, alone orin combination with scripts in JAVASCRIPT, other scripting languages andother programming source text. In another embodiment, the programmedinstructions also may represent one or more files or projects of sourcecode that are digitally stored in a mass storage device such asnon-volatile RAM or disk storage, in the systems of FIG. 1 or a separaterepository system, which when compiled or interpreted cause generatingexecutable instructions which when executed cause the computer toperform the functions or operations that are described herein withreference to those instructions. In other words, the drawing figure mayrepresent the manner in which programmers or software developersorganize and arrange source code for later compilation into anexecutable, or interpretation into bytecode or the equivalent, forexecution by the server computer 102.

Network 114 broadly represents any medium or mechanism that provides forthe exchange of data between the various elements of FIG. 1. Examples ofnetwork 114 include, without limitation, a cellular network,communicatively coupled with a data connection to the computing devicesover a cellular antenna, one or more Local Area Networks (LANs), one ormore Wide Area Networks (WANs), one or more Ethernets or the Internet,or one or more terrestrial, satellite or wireless links, or acombination thereof. For purposes of illustrating a clear example,network 114 is shown as a single element but in practice, network 114may comprise one or more local area networks, wide area networks, and/orinternetworks. The various elements of FIG. 1 may also have direct(wired or wireless) communications links, depending upon a particularimplementation.

The computing devices such as the Buyer Computer 118 and SupplierComputer 120 may comprise a desktop computer, laptop computer, tabletcomputer, smartphone, or any other type of computing device that allowsaccess to the server 102. The Buyer Computer 118 may be associated withone or more buyers. The Supplier Computer 120 may be associated with oneor more suppliers.

FIG. 1 depicts server computer 102 as a distinct element for the purposeof illustrating a clear example. However, in other embodiments, more orfewer server computers may accomplish the functions described herein.Additionally, server computer 102 may comprise a plurality ofcommunicatively coupled server computers including a server computer forstoring past transaction data.

3.0 METHOD OVERVIEW

FIG. 4 is a flowchart of an example method of providing automatedinformation requests based on supplier risk analysis, according tovarious embodiments.

For purposes of illustrating a clear example, FIG. 4 is described hereinin the context of FIG. 1, but the broad principles of FIG. 4 can beapplied to other systems having configurations other than as shown inFIG. 1. Further, FIG. 4 and each other flow diagram herein illustratesan algorithm or plan that may be used as a basis for programming one ormore of the functional modules of FIG. 1 that relate to the functionsthat are illustrated in the diagram, using a programming developmentenvironment or programming language that is deemed suitable for thetask. Thus, FIG. 4 and each other flow diagram herein are intended as anillustration at the functional level at which skilled persons, in theart to which this disclosure pertains, communicate with one another todescribe and implement algorithms using programming. The flow diagramsare not intended to illustrate every instruction, method object or substep that would be needed to program every aspect of a working program,but are provided at the high, functional level of illustration that isnormally used at the high level of skill in this art to communicate thebasis of developing working programs.

In step 402, a selection of a supplier identifier value that identifiesa supplier during a supplier onboarding process in an e-procurementsystem is received. For example, the server 102 or e-procurement system108 may receive a selection of a supplier identifier value from buyercomputer 118.

Referring now to FIG. 5, which illustrates an example graphical userinterface (GUI) of a digital display device, which may be generatedunder program control using the techniques herein for selecting a typeof form for onboarding a supplier, a form type may be selected toinitiate the supplier onboarding process. In an embodiment, a GUI 500comprises a plurality of hyperlinked graphical buttons 502, 504, 506,508 that are programmed to invoke different form types. Form typeselections may include selections to onboard a North American Supplier,a European Supplier, and general supplier onboarding using hyperlinkedgraphical buttons 502, 504, 506, 508. When a “Onboard supplier” button502, 504, 506, 508 is selected, a supplier onboarding form is displayed,such as shown in FIG. 6. The appearance and labeling of buttons 502,504, 506, 508 in FIG. 5 are examples and other embodiments may usefunctionally equivalent links or widgets having different format andlabeling.

FIG. 6 illustrates a supplier onboarding form that is programmed foronboarding North America Suppliers. In an embodiment, an onboarding form600 includes data entry fields such as the Name of a supplier 602 andprimary contract data entry fields such as the First Name 604, Last Name606, Email 608, Mobile Phone 610, Work Phone 612, and Fax 614 of theprimary contact of the supplier. Each of the fields 602, 604, 606, 608,610, 612, 614 may be programmed as a data input field using HTML formsor similar techniques. As shown in FIG. 6, data entry fields 602-614 canbe manually populated to select a supplier that a buyer seeks to onboardto the e-procurement system.

In an embodiment, the supplier onboarding form of FIG. 6 includes anoption 616 to Find a Supplier and includes options 618, 620 622 that areprogrammed to Cancel, Save, and Preview the supplier onboarding form. Inan embodiment, when Find Supplier button 616 is selected, in response, aGUI for searching and selecting a supplier is displayed, as shown inFIG. 7.

FIG. 7 illustrates a GUI that is programmed to support searching andselecting a supplier during the supplier onboarding process. The GUI 700includes a search entry field 702 that is programmed to accept searchqueries for searching for suppliers. In response to receiving a searchquery in field 702, the system is programmed to perform a databasesearch and the GUI displays results of the search. In the example ofFIG. 7, the query “San Mateo Piano Co.” yielded 41 suppliers as aresult, and details for two (2) results 706, 708 are shown in thesections titled “San Mateo Piano Co.” and “Mateo Movers of Piano”.

The GUI 700 of FIG. 7 also illustrates search filters 704 that may beselected and are programmed to cause re-displaying search results in theGUI for only those results that match the selected filters. Examples offilters include “Supplier Health”, “Supplier Relationship”, “SupplierRating”, “Supplier Certifications”, and “Ship To Countries” that can beused to refine the results of the search. In an embodiment, the SupplierHealth filter 704 may include radio buttons for selecting Best in Class,Trusted, Unclassified or other health values. In an embodiment, theSupplier Relationship filter 704 may include radio buttons for selectinga value of Existing or Community to permit filtering for suppliers thathave an existing relationship to the entity of the client computer orthat are within a procurement community. In an embodiment, the SupplierRating filter 704 may include radio buttons for selecting rating valuessuch as five stars, three stars and others. In an embodiment, theSupplier Certifications filter 704 may include radio buttons forselecting from among certifications that have been earned by one or moresuppliers in the results. In an embodiment, the Ship To Countries filter704 may comprise a drop-down menu that is programmed to display thecountries to which different suppliers in the results will ship goods.

Each of the search results 706, 708 includes information relating to arespective supplier such as a supplier name, supplier address, primarycontact information, supplier shipping information, and platformspecific information. Each search result 706, 708 includes risk scoredetails 710, 714 associated with the respective supplier. In anembodiment, risk score details 710, 714 comprise numeric values for oneor more of, or all of, “Financial Score”, “Judicial Score”, “ScreeningLists”, “News Sentiment Score”, “Disputes”, “Overages”, and “RejectedInvoices”.

In an embodiment, the financial score value represents a rating of thesupplier based upon financial indicators such as a third-party creditrating score value, a count of previous late payments, and/or arepresentation of whether the supplier has ever entered bankruptcy. Inan embodiment, a judicial score value is based upon publicly availablelegal status databases and represents a number of lawsuits filed againstthe supplier, such as collections actions. In an embodiment, thescreening lists value is calculated based on whether the supplierappears in a government list such as a sanctions list, banned importeror exporter list, or a list of suppliers that are prohibited ingovernment contracting. In an embodiment, the news sentiment score valuerepresents a sentiment value calculated by third-party sentimentcalculation services based upon sentiments expressed in social mediapostings about the supplier. In an embodiment, the disputes score isbased on the number of invoice disputes that a supplier has had with theclient computer's entity or with a community of buyers. In anembodiment, the overages score is based on the number of overchargedisputes that a supplier has had with the client computer's entity orwith a community of buyers. In an embodiment, the rejected invoicesscore is based on the number of rejected invoices that a supplier hashad with the client computer's entity or with a community of buyers. Theappearance of these score values within search results 706, 708 promotesefficiency in the onboarding of supplier data by alerting a clientcomputer to material reasons to accept, or reject, a particularsupplier. When a client computer rejects a particular supplier basedupon one or more of the score values, the result is reduction in thenumber of network messages, storage, bandwidth and CPU resources thatotherwise would be required to investigate the supplier and then rejectits data. Furthermore, when a client computer accepts a particularsupplier based on the score values, the client computer also avoidsnetwork messages, storage, bandwidth and CPU resources that otherwisewould be required to investigate the supplier and accept its data. Inthe example of FIG. 7, at least six (6) network messages, responses andassociated displays of data are avoided by the instant display of thescore values, because otherwise the client computer would have torequest and receive the individual score values or their foundation datafrom one or more other systems.

A supplier can be selected for onboarding by selecting one of the“Select Supplier” buttons 712, 716. In an embodiment, supplieronboarding in an e-procurement system is the process of collectingdocumentation and data needed to set up a company as an approvedsupplier and to enable buyers to efficiently conduct business, purchasegoods and services, and make payments to that company.

In an embodiment, supplier onboarding is a process for a buyer to setupa new supplying organization so the buyer can efficiently send purchaseorders, receive invoices, and manage contracts with the supplyingorganization. During onboarding, buyers need to collect information fromthe supplier to set them up in the e-procurement system so they can paythe supplier as well as have all the information needed for taxes,external compliance (anti-terrorism, anti-money laundering, etc.), andinternal compliance (diversity programs, CSR, workers rights policies,and financial and reputation risk policies).

The features in this application help with this on many fronts, byhelping the buying user find information that already exists in Coupa'scommunity of supplier data, they can save time on finding and enteringinformation as well as ensure that they are using information that hasbeen vetted by another buying company. The buying company can also now,with the features in this application, directly see risk factors andscreening list red flags to help them better decide whether to onboardthe supplier or investigate a risk factor or red flag further.

Supplier onboarding is further described in provisional application No.62,446,864, filed Jan. 17, 2017, the entire contents of which areincorporated by reference as if fully disclosed herein.

Referring again to FIG. 4, in step 404, a digital data repository of thee-procurement system is queried to seek a data record matching theselected supplier identifier value. For example, the server computer 102may query the e-procurement system 108 to retrieve a data record fromthe transactional database 110 that matches the selected supplieridentifier value.

As discussed with respect to step 402, a supplier can be selected bymanually populating the supplier onboarding form as illustrated in FIG.6 or by searching and selecting a supplier as illustrated by FIG. 7.

In step 406, in response to determining that the data repository has arecord matching the selected supplier identifier, a risk score valueassociated with the selected supplier identifier is identified from adataset of risk score values that is stored in the data repository. Forexample, the server computer 102 may determine that the data recordretrieved from the query in step 404 matches the selected supplieridentifier. The server may then query the e-procurement system 108 for arisk score value associated with the selected supplier identifier.

As discussed with respect to steps 402 and 404, when a supplier isselected by manually populating the supplier onboarding form asillustrated by FIG. 6, the selected supplier is matched to a record fromthe e-procurement system. Alternatively, as discussed herein, the GUI ofFIG. 7 may be used to select a supplier during the supplier onboardingprocess that matches a record from the e-procurement system.

When a record is found in the e-procurement system that matches theselected supplier, a risk score associated with the selected supplier isdisplayed. FIG. 8 illustrates an example GUI for displaying risk scoredata and supplier details during a supplier onboarding process. As shownin the example of FIG. 8, risk score details 802 and known supplierdetails 804 are displayed to the buyer computer during the supplieronboarding process above the supplier onboarding form 806. The supplieronboarding form may be the same onboarding form as discussed in step 402with respect to FIG. 6. The known supplier details 804 include detailssuch as the professional name of the company, the website of thesupplier, primary contact information, star rating. basic shipping data,and e-procurement platform related information. The risk score details802 include risk score components such as: “Financial Score”, “JudicialScore”, “Screening Lists”, “News Sentiment Score”, “Disputes”,“Overages”, and “Rejected Invoices”.

Risk score values may be utilized to provide a risk assessment of aparticular supplier. One use of risk score values in the e-procurementcontext is further described in U.S. application Ser. No. 15/683,689,filed Aug. 22, 2017, the entire contents of which are incorporated byreference as if fully disclosed herein.

In an embodiment, a matching record may include an exact match or anormalized match. For example, a particular supplier can be representedin the e-procurement system as multiple different vendors, wherein eachvendor associated with a different supplier identifier value. Whensupplier identifier values differ, the server computer may use differenttechniques to determine whether two supplier identifier values refer tothe same supplier. For example, the server computer may determinewhether profile data associated with each supplier identifier valuematches. For example, the server will determine whether a website URLmatches between the suppliers or whether other contact information, suchas phone number or address, match between the suppliers.

In an embodiment, the server computer trains a machine learning tool fornormalizing supplier identifiers. For example, training datasets may begenerated based on prior transactions that were already identified asbeing associated with specific suppliers, such as through manualverification. The server computer may train the machine learning networkusing the training datasets which include transaction data and supplieridentifiers. The server computer may then use transactions withoutidentified suppliers as input into the machine learning model in orderto identify suppliers from the transaction data.

Normalizing the supplier identifiers may generally include selecting aparticular supplier identifier for a supplier and storing data with eachtransaction that identifies the supplier using the particular supplieridentifier. For example, if R&M is selected as the normalized supplieridentifier for a particular supplier, then the server computer mayadjust non-matching supplier identifiers that have been identified asbeing associated with the particular supplier, such as M&R, to match thesupplier identifier of R&M.

Selection of the identifier to which the supplier identifiers are to benormalized may be based on frequency of the identifiers and/or onspecific selections of the identifiers. For example, if the supplier hasa profile through a transaction management system hosted by the servercomputer, then the server computer may use the supplier name from thesupplier profile as the normalized identifier. Additionally oralternatively, the supplier identifier for normalization may be manuallyselected during verification of training data for the machine learningmodel. Thus, the machine learning model may be configured to outputnormalized supplier identifiers for each of the transactions.

Supplier normalization in the digital e-procurement context is furtherdescribed in U.S. application Ser. No. 15/815,497, filed Nov. 16, 2017,the entire contents of which are incorporated by reference as if fullydisclosed herein.

In an embodiment, in response to determining that the data repositorydoes not have a record matching the selected supplier identifier, a riskscore value may be generated for the selected supplier identifier valuein real time, stored in association with the supplier identifier value,and displayed to the buyer during the onboarding process. Thus, theintegration of risk score displays as seen in FIG. 8 to the supplieronboarding process provides distinct benefits in terms of reducing thenumber of mouse clicks, network messages, accesses to external systems,and other use of bandwidth, CPU, memory and storage resources ascompared to not displaying that information as described herein. Thedisplay of FIG. 8 when integrated with the complete workflow describedherein solves the technical problem of how to obtain all data relevantto a supplier risk assessment at the time when it is needed the most,that is, when a buyer computer or other client computer is executingsteps to add a potential supplier to a system. By integrating uniquelygenerated risk scores to the supplier onboarding process state, thisimprovement assists the average buyer by aggregating necessaryinformation components and presenting Without this improvement, theaverage buyer lacks enough detailed information to make an informeddecision regarding purchasing and would end up spending valuable timeand computing resources to search for and find the risk scoreinformation in different parts of the e-procurement system. Thisimprovement brings risk assessments to the supplier onboarding processand provides the custom functionality to further assess a supplier withautomated custom forms.

In step 408, a unique mapping table is generated in digital memory thatmaps each supplier risk score value of one or more supplier risk scorevalues to one or more information request identifiers, the one or moresupplier risk score values including the risk score value associatedwith the selected supplier identifier value. For example, the MappingGenerating Instructions 104 may generate a unique mapping table thatmaps supplier risk values to information request identifiers.

In some embodiments, an information request identifier comprises atextual question or statement that indicates a request for information.

For example, FIG. 2 illustrates a unique mapping table that mapssupplier risk score values 202 to information request identifiers 204.In FIG. 2, each supplier risk score value is mapped to one or moreinformation request identifiers. For example, risk score value ‘99’ ismapped to information request identifier “Provide updated information”.Risk score value ‘95’ is mapped to information request identifiers: “Whywere your reported earnings below expectation last quarter?”, “How manylawsuits are ongoing where your company is a party?”, and “How manytimes in the last year has your company been sued?”.

In some embodiments, components of supplier risk score values are mappedto information request identifiers. For example, supplier financialscore values, which are used along with judicial score values and newssentiment score values to calculate an overall risk score value, areeach individually mapped to information request identifiers.

For example, FIG. 3 illustrates a unique mapping table that maps riskscore component values 302, 304, 306 to information request identifiers308. Each risk score component value maps to different informationrequest identifiers. For example, Supplier Financial Score Value ‘99’ ismapped to information request identifier “Why is your credit score below600?”. Supplier News Sentiment Score Value ‘98’ is mapped to informationrequest identifier “Why have you received negative press in the lastmonth?”. In this example, risk score component categories includeSupplier Financial Score Values 302, Supplier Judicial Score Values 304,and Supplier News Sentiment Score Values 306.

Referring again to FIG. 4, in step 410, a custom digital data entry formis generated comprising one or more information request fields that aremapped to the risk score value associated with the selected supplieridentifier. For example, the Data Form Generating Instructions 106 maygenerate a custom digital data entry form by using the unique mappingtable generated in step 208.

The custom digital data entry form defines what information is to becollected from the supplier. The form may vary according to the mappinggenerated in step 408.

In step 412, the custom data entry form is digitally transmitted to acomputer associated with the supplier corresponding to the selectedsupplier, the custom data form prompting the supplier to take action,respond, or contribute information back to the server computer. Forexample, the server 102 may transmit the form to the supplier computer.Upon delivery, the form may prompt the supplier computer to process theform.

In an embodiment, the prompt can be by calendaring a to-do item, sendinga text, sending a preformulated email message, leaving a preformulatedphone message, or any other means. The form can be made available as anattachment, directly through a link, through access to a web site, etc.The form can then be processed and the server 102 can be programmed tobe notified in various ways accordingly. For example, the server 102 canverify whether all the fields in the form have been filled out orwhether the form has been edited at all within a specific time period.The server 102 can also be configured to periodically poll the recipientor consider the form processed upon receipt of a confirmation from therecipient.

For example, FIG. 10 illustrates a basic data entry form prompt in emailformat. The prompt 1002 directs the supplier to update the supplierprofile information on the Coupa system. When a buyer selects the SendInfo Request button 1004, the data entry form prompt is transmitted tothe supplier.

In one embodiment, the server causes transmitting, to a specified e-mailaddress of a supplier, an e-mail message containing hyperlinks thatinvoke operation of the e-procurement system at specified dynamic webpages or forms that are programmed to receive data from the supplier,regardless of whether the supplier logs-in or completes anauthentication with the e-procurement system. For example, initiating arequisition may cause the e-procurement system to dispatch an e-mailmessage that contains hyperlinks acting as callbacks into thee-procurement system. When the e-mail is opened and the hyperlinks areselected, a supplier computer (separate from the buyer) receives adynamically generated web page or form in which to enter data.

In an embodiment, the custom data entry form is transmitted as a uniquehyperlink to a security sandboxed webpage. Security sandboxed webpagesin context of e-procurement systems are discussed in U.S. patentapplication Ser. No. 14/504,721, filed Oct. 2, 2014, the entire contentsof which are incorporated by reference as if fully disclosed herein.

ALTERNATIVE EMBODIMENTS

In an embodiment, once a supplier is onboarded in the e-procurementsystem, a buyer computer may access details associated with the supplierby browsing and exploring different suppliers through the e-procurementsystem. A buyer computer may also access details associated with thesupplier when creating a purchase order in association with a supplier.Browsing and exploring different suppliers is discussed in U.S.application Ser. No. 15/815,497, filed Nov. 16, 2017, the entirecontents of which are incorporated by reference as if fully disclosedherein.

As shown in FIG. 9, if a supplier has already been onboarded to thee-procurement system, a buyer may view the supplier health informationand risk score details associated with the selected supplier identifier.For example, supplier health information 902 shows a graphicalrepresentation of supplier risk. Health information includes data pointssuch as a Supplier Health Score, Supplier Performance percentages, and aplatform wide rating. Risk Score Details 904 shows risk score componentssuch as: “Financial Score”, “Judicial Score”, “News Sentiment Score”,“Screening Lists”, and the corresponding values. Recommendations 906shows platform recommendation options such as the option to viewalternative suppliers, request information, and put the supplier onhold. By selecting the “Request Info (SIM)” button in theRecommendations 906 section, a data entry form prompt such as discussedwith respect to FIG. 10 may be generated.

In an embodiment, steps 402-406 may be replaced or supplemented by thesteps of: receiving, by a server computer, a selection of a supplieridentifier value that identifies an existing supplier in ane-procurement system and querying, by the server computer, a digitaldata repository of the e-procurement system to identify a risk scorevalue associated with the selected supplier identifier value from adataset of risk score values that is stored in the data repository Forexample, if a supplier has already been onboarded into the e-procurementsystem, a buyer may browse different suppliers and view the risk scorevalues associated with onboarded suppliers, as discussed herein withrespect to FIG. 6.

In an embodiment, information contributed by the selected supplier inresponse to the transmission of the custom data form to the selectedsupplier is received by the server computer. In response to receivinginformation contributed by the selected supplier, automaticallyapproving the selected supplier in the e-procurement system. Forexample, the information contributed by the selected supplier inresponse to the transmission of the custom data form may cause theupdating of the risk score value associated with the selected supplier.If the risk score value associated with the selected supplier is above athreshold value after the updating, the selected supplier will beautomatically approved in the e-procurement system.

In an embodiment, information contributed by the selected supplier inresponse to the transmission of the custom data form to the selectedsupplier is received by the server computer. In response to receivinginformation contributed by the selected supplier, automaticallyrejecting the selected supplier from being onboarded in thee-procurement system based on the risk score value associated with theselected supplier. For example, the information contributed by theselected supplier in response to the transmission of the custom dataform may cause the updating of the risk score value associated with theselected supplier. If the risk score value associated with the selectedsupplier after the updating is below a threshold value, the selectedsupplier will be automatically rejected from being onboarded in thee-procurement system.

4.0 IMPLEMENTATION EXAMPLE—HARDWARE OVERVIEW

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 11 illustrates a computer system 1100 upon which anembodiment of the invention may be implemented. Computer system 1100includes a bus 1102 or other communication mechanism for communicatinginformation, and a hardware processor 1104 coupled with bus 1102 forprocessing information. Hardware processor 1104 may be, for example, ageneral-purpose microprocessor.

Computer system 1100 also includes a main memory 1106, such as arandom-access memory (RAM) or other dynamic storage device, coupled tobus 1102 for storing information and instructions to be executed byprocessor 1104. Main memory 1106 also may be used for storing temporaryvariables or other intermediate information during execution ofinstructions to be executed by processor 1104. Such instructions, whenstored in non-transitory storage media accessible to processor 1104,render computer system 1100 into a special-purpose machine that iscustomized to perform the operations specified in the instructions.

Computer system 1100 further includes a read-only memory (ROM) 1108 orother static storage device coupled to bus 1102 for storing staticinformation and instructions for processor 1104. A storage device 1110,such as a magnetic disk or optical disk, is provided and coupled to bus1102 for storing information and instructions.

Computer system 1100 may be coupled via bus 1102 to a display 1112, suchas a cathode ray tube (CRT), for displaying information to a computeruser. An input device 1114, including alphanumeric and other keys, iscoupled to bus 1102 for communicating information and command selectionsto processor 1104. Another type of user input device is cursor control1116, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor1104 and for controlling cursor movement on display 1112. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane.

Computer system 1100 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 1100 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 1100 in response to processor 1104 executing one or moresequences of one or more instructions contained in main memory 1106.Such instructions may be read into main memory 1106 from another storagemedium, such as storage device 1110. Execution of the sequences ofinstructions contained in main memory 1106 causes processor 1104 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperation in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical or magnetic disks, such as storage device 1110.Volatile media includes dynamic memory, such as main memory 1106. Commonforms of storage media include, for example, a floppy disk, a flexibledisk, hard disk, solid state drive, magnetic tape, or any other magneticdata storage medium, a CD-ROM, any other optical data storage medium,any physical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 1102. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 1104 for execution. Forexample, the instructions may initially be carried on a magnetic disk orsolid state drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 1100 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 1102. Bus 1102 carries the data tomain memory 1106, from which processor 1104 retrieves and executes theinstructions. The instructions received by main memory 1106 mayoptionally be stored on storage device 1110 either before or afterexecution by processor 1104.

Computer system 1100 also includes a communication interface 1118coupled to bus 1102. Communication interface 1118 provides a two-waydata communication coupling to a network link 1120 that is connected toa local network 1122. For example, communication interface 1118 may bean integrated services digital network (ISDN) card, cable modem,satellite modem, or a modem to provide a data communication connectionto a corresponding type of telephone line. As another example,communication interface 1118 may be a local area network (LAN) card toprovide a data communication connection to a compatible LAN. Wirelesslinks may also be implemented. In any such implementation, communicationinterface 1118 sends and receives electrical, electromagnetic or opticalsignals that carry digital data streams representing various types ofinformation.

Network link 1120 typically provides data communication through one ormore networks to other data devices. For example, network link 1120 mayprovide a connection through local network 1122 to a host computer 1124or to data equipment operated by an Internet Service Provider (ISP)1126. ISP 1126 in turn provides data communication services through theworld-wide packet data communication network now commonly referred to asthe “Internet” 1128. Local network 1122 and Internet 1128 both useelectrical, electromagnetic or optical signals that carry digital datastreams. The signals through the various networks and the signals onnetwork link 1120 and through communication interface 1118, which carrythe digital data to and from computer system 1100, are example forms oftransmission media.

Computer system 1100 can send messages and receive data, includingprogram code, through the network(s), network link 1120 andcommunication interface 1118. In the Internet example, a device 1130might transmit a requested code for an application program throughInternet 1128, ISP 1126, local network 1122 and communication interface1118.

The received code may be executed by processor 1104 as it is received,and/or stored in storage device 1110, or other non-volatile storage forlater execution.

5.0 OTHER ASPECTS OF DISCLOSURE

Although some of the figures described in the foregoing specificationinclude flow diagrams with steps that are shown in an order, the stepsmay be performed in any order, and are not limited to the order shown inthose flowcharts. Additionally, some steps may be optional, may beperformed multiple times, and/or may be performed by differentcomponents. All steps, operations and functions of a flow diagram thatare described herein are intended to indicate operations that areperformed using programming in a special-purpose computer orgeneral-purpose computer, in various embodiments. In other words, eachflow diagram in this disclosure, in combination with the related textherein, is a guide, plan or specification of all or part of an algorithmfor programming a computer to execute the functions that are described.The level of skill in the field associated with this disclosure is knownto be high, and therefore the flow diagrams and related text in thisdisclosure have been prepared to convey information at a level ofsufficiency and detail that is normally expected in the field whenskilled persons communicate among themselves with respect to programs,algorithms and their implementation.

In the foregoing specification, the example embodiment(s) of the presentinvention have been described with reference to numerous specificdetails. However, the details may vary from implementation toimplementation according to the requirements of the particular implementat hand. The example embodiment(s) are, accordingly, to be regarded inan illustrative rather than a restrictive sense.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a server computer, a selection of a supplier identifiervalue that identifies a selected supplier during a supplier onboardingprocess in an e-procurement system; querying, by the server computer, adigital data repository of the e-procurement system to seek a datarecord matching the selected supplier identifier value; in response todetermining that the data repository has a record matching the selectedsupplier identifier value, identifying a supplier risk score valueassociated with the selected supplier identifier value from a dataset ofsupplier risk score values that is stored in the data repository; beforethe selected supplier is approved in the e-procurement system,generating in digital memory a unique mapping table that maps eachsupplier risk score value of one or more supplier risk score values toone or more information request identifiers of a plurality ofinformation request identifiers, the one or more supplier risk scorevalues including the supplier risk score value associated with theselected supplier identifier value, each information request identifierof the plurality of information request identifiers comprising a textualquestion or statement that indicates a request for information; beforethe selected supplier is approved in the e-procurement system,generating, by the server computer, a custom digital data entry formcomprising the one or more information request identifiers of theplurality of information request identifiers that are mapped to thesupplier risk score value associated with the selected supplieridentifier value in the unique mapping table; digitally transmitting, bythe server computer, to a specified e-mail address of the selectedsupplier, an e-mail message containing hyperlinks that invoke operationof the e-procurement system at a security sandboxed webpage, thesecurity sandboxed webpage displaying the custom digital data entryform, the custom digital data entry form prompting the selected supplierto take action, respond, or contribute information back to the servercomputer; receiving, by the server computer, information contributed bythe selected supplier in response to the transmission of the e-mailmessage to the specified e-mail address of the selected supplier; inresponse to receiving information contributed by the selected supplier,updating the supplier risk score value associated with the selectedsupplier identifier value based on the information contributed by theselected supplier; in response to determining that the updated supplierrisk score value associated with the selected supplier identifier valueis above a threshold value, automatically approving the selectedsupplier in the e-procurement system; in response to determining thatthe updated supplier risk score value associated with the selectedsupplier identifier value is below the threshold value, automaticallyrejecting the selected supplier from being onboarded in thee-procurement system; wherein the method is performed by one or morecomputing devices.
 2. The method of claim 1, further comprising: inresponse to determining that the digital data repository does notinclude a record matching the selected supplier identifier, generating asupplier risk score value for the selected supplier identifier andstoring the risk score value in a new record in the digital datarepository that matches the selected supplier identifier.
 3. The methodof claim 1, wherein a supplier risk score value represents a risk thatthe supplier will default on a supply transaction and is calculatedbased on a plurality of data items that represent historic performanceof the supplier.
 4. The method of claim 1, wherein the supplier riskscore value represents a risk that the supplier will default on a supplytransaction and is calculated based on a financial score value thatrepresents a rating of the supplier based upon financial indicators suchas a third-party credit rating score value, a count of previous latepayments, and/or a representation of whether the supplier has everentered bankruptcy, a judicial score value that represents a number oflawsuits filed against the supplier, and a news sentiment score valuethat represents a sentiment value calculated by third-party sentimentcalculation services based upon sentiments expressed in social mediapostings about the supplier.
 5. The method of claim 4, furthercomprising: generating a unique mapping of each financial score value,judicial score value, and news sentiment score value to one or moreinformation request identifiers, the financial score value, judicialscore value, and news sentiment score value associated with the selectedsupplier.
 6. The method of claim 1, wherein a supplier risk score valuerepresents a risk that the supplier will default on a supply transactionand is calculated based on a plurality of data items that representhistoric performance of the supplier.
 7. The method of claim 1, whereinthe supplier risk score value represents a risk that the supplier willdefault on a supply transaction and is calculated based on a financialscore value that represents a rating of the supplier based uponfinancial indicators such as a third-party credit rating score value, acount of previous late payments, and/or a representation of whether thesupplier has ever entered bankruptcy, a judicial score value thatrepresents a number of lawsuits filed against the supplier, and a newssentiment score value that represents a sentiment value calculated bythird-party sentiment calculation services based upon sentimentsexpressed in social media postings about the supplier.
 8. The method ofclaim 7, further comprising: generating a unique mapping of eachfinancial score value, judicial score value, and news sentiment scorevalue to one or more information request identifiers, the financialscore value, judicial score value, and news sentiment score valueassociated with the selected supplier.
 9. A computer-implemented methodcomprising: receiving, by a server computer, a selection of a supplieridentifier value that identifies an existing supplier in ane-procurement system; querying, by the server computer, a digital datarepository of the e-procurement system to identify a supplier risk scorevalue associated with the selected supplier identifier value from adataset of supplier risk score values that is stored in the datarepository; before the selected supplier is approved in thee-procurement system, generating in digital memory a unique mappingtable that maps each supplier risk score value of one or more supplierrisk score values to one or more information request identifiers of aplurality of information request identifiers, the one or more supplierrisk score values including the supplier risk score value associatedwith the selected supplier identifier value, each information requestidentifier of the plurality of information request identifierscomprising a textual question or statement that indicates a request forinformation; before the selected supplier is approved in thee-procurement system, generating, by the server computer, a customdigital data entry form comprising the one or more information requestidentifiers of the plurality of information request identifiers that aremapped to the supplier risk score value associated with the selectedsupplier identifier value in the unique mapping table; digitallytransmitting, by the server computer, to a specified e-mail address ofthe selected supplier, an e-mail message containing hyperlinks thatinvoke operation of the e-procurement system at a security sandboxedwebpage, the security sandboxed webpage displaying the custom digitaldata entry form, the custom digital data entry form prompting theselected supplier to take action, respond, or contribute informationback to the server computer; receiving, by the server computer,information contributed by the selected supplier in response to thetransmission of the e-mail message to the specified e-mail address ofthe selected supplier; in response to receiving information contributedby the selected supplier, updating the supplier risk score valueassociated with the selected supplier identifier value based on theinformation contributed by the selected supplier; in response todetermining that the updated supplier risk score value associated withthe selected supplier identifier value is above a threshold value,automatically approving the selected supplier in the e-procurementsystem; in response to determining that the updated supplier risk scorevalue associated with the selected supplier identifier value is belowthe threshold value, automatically rejecting the selected supplier frombeing onboarded in the e-procurement system; wherein the method isperformed by one or more computing devices.
 10. The method of claim 9,wherein the existing supplier has already been onboarded during asupplier onboarding process in the e-procurement system.
 11. A dataprocessing system comprising: one or more hardware processors; anon-transitory computer-readable medium having instructions embodiedthereon, the instructions, when executed by the one or more processors,cause: receiving, by a server computer, a selection of a supplieridentifier value that identifies a selected supplier during a supplieronboarding process in an e-procurement system; querying, by the servercomputer, a digital data repository of the e-procurement system to seeka data record matching the selected supplier identifier value; inresponse to determining that the data repository has a record matchingthe selected supplier identifier value, identifying a supplier riskscore value associated with the selected supplier identifier value froma dataset of supplier risk score values that is stored in the datarepository; before the selected supplier is approved in thee-procurement system, generating in digital memory a unique mappingtable that maps each supplier risk score value of one or more supplierrisk score values to one or more information request identifiers of aplurality of information request identifiers, the one or more supplierrisk score values including the supplier risk score value associatedwith the selected supplier identifier value, each information requestidentifier of the plurality of information request identifierscomprising a textual question or statement that indicates a request forinformation; before the selected supplier is approved in thee-procurement system, generating, by the server computer, a customdigital data entry form comprising the one or more information requestidentifiers of the plurality of information request identifiers that aremapped to the supplier risk score value associated with the selectedsupplier identifier value in the unique mapping table; digitallytransmitting, by the server computer, to a specified e-mail address ofthe selected supplier, an e-mail message containing hyperlinks thatinvoke operation of the e-procurement system at a security sandboxedwebpage, the security sandboxed webpage displaying the custom digitaldata entry form, the custom digital data entry form prompting theselected supplier to take action, respond, or contribute informationback to the server computer; receiving, by the server computer,information contributed by the selected supplier in response to thetransmission of the e-mail message to the specified e-mail address ofthe selected supplier; in response to receiving information contributedby the selected supplier, updating the supplier risk score valueassociated with the selected supplier identifier value based on theinformation contributed by the selected supplier; in response todetermining that the updated supplier risk score value associated withthe selected supplier identifier value is above a threshold value,automatically approving the selected supplier in the e-procurementsystem; in response to determining that the updated supplier risk scorevalue associated with the selected supplier identifier value is belowthe threshold value, automatically rejecting the selected supplier frombeing onboarded in the e-procurement system.
 12. The system of claim 11,further comprising: in response to determining that the digital datarepository does not include a record matching the selected supplieridentifier, generating a supplier risk score value for the selectedsupplier identifier and storing the risk score value in a new record inthe digital data repository that matches the selected supplieridentifier.
 13. The system of claim 11, wherein a supplier risk scorevalue represents a risk that the supplier will default on a supplytransaction and is calculated based on a plurality of data items thatrepresent historic performance of the supplier.
 14. The system of claim11, wherein the supplier risk score value represents a risk that thesupplier will default on a supply transaction and is calculated based ona financial score value that represents a rating of the supplier basedupon financial indicators such as a third-party credit rating scorevalue, a count of previous late payments, and/or a representation ofwhether the supplier has ever entered bankruptcy, a judicial score valuethat represents a number of lawsuits filed against the supplier, and anews sentiment score value that represents a sentiment value calculatedby third-party sentiment calculation services based upon sentimentsexpressed in social media postings about the supplier.
 15. The system ofclaim 11, further comprising: generating a unique mapping of eachfinancial score value, judicial score value, and news sentiment scorevalue to one or more information request identifiers, the financialscore value, judicial score value, and news sentiment score valueassociated with the selected supplier.
 16. A data processing systemcomprising: one or more hardware processors; a non-transitorycomputer-readable medium having instructions embodied thereon, theinstructions, when executed by the one or more processors, cause:receiving, by a server computer, a selection of a supplier identifiervalue that identifies an existing supplier in an e-procurement system;querying, by the server computer, a digital data repository of thee-procurement system to identify a supplier risk score value associatedwith the selected supplier identifier value from a dataset of supplierrisk score values that is stored in the data repository; before theselected supplier is approved in the e-procurement system, generating indigital memory a unique mapping table that maps each supplier risk scorevalue of one or more supplier risk score values to one or moreinformation request identifiers of a plurality of information requestidentifiers, the one or more supplier risk score values including thesupplier risk score value associated with the selected supplieridentifier value, each information request identifier of the pluralityof information request identifiers comprising a textual question orstatement that indicates a request for information; before the selectedsupplier is approved in the e-procurement system, generating, by theserver computer, a custom digital data entry form comprising the one ormore information request identifiers of the plurality of informationrequest identifiers that are mapped to the supplier risk score valueassociated with the selected supplier identifier value in the uniquemapping table; digitally transmitting, by the server computer, to aspecified e-mail address of the selected supplier, an e-mail messagecontaining hyperlinks that invoke operation of the e-procurement systemat a security sandboxed webpage, the security sandboxed webpagedisplaying the custom digital data entry form, the custom digital dataentry form prompting the selected supplier to take action, respond, orcontribute information back to the server computer; receiving, by theserver computer, information contributed by the selected supplier inresponse to the transmission of the e-mail message to the specifiede-mail address of the selected supplier; in response to receivinginformation contributed by the selected supplier, updating the supplierrisk score value associated with the selected supplier identifier valuebased on the information contributed by the selected supplier; inresponse to determining that the updated supplier risk score valueassociated with the selected supplier identifier value is above athreshold value, automatically approving the selected supplier in thee-procurement system; in response to determining that the updatedsupplier risk score value associated with the selected supplieridentifier value is below the threshold value, automatically rejectingthe selected supplier from being onboarded in the e-procurement system.17. The system of claim 16, wherein a supplier risk score valuerepresents a risk that the supplier will default on a supply transactionand is calculated based on a plurality of data items that representhistoric performance of the supplier.
 18. The system of claim 16,wherein the supplier risk score value represents a risk that thesupplier will default on a supply transaction and is calculated based ona financial score value that represents a rating of the supplier basedupon financial indicators such as a third-party credit rating scorevalue, a count of previous late payments, and/or a representation ofwhether the supplier has ever entered bankruptcy, a judicial score valuethat represents a number of lawsuits filed against the supplier, and anews sentiment score value that represents a sentiment value calculatedby third-party sentiment calculation services based upon sentimentsexpressed in social media postings about the supplier.
 19. The system ofclaim 16, further comprising: generating a unique mapping of eachfinancial score value, judicial score value, and news sentiment scorevalue to one or more information request identifiers, the financialscore value, judicial score value, and news sentiment score valueassociated with the selected supplier.
 20. The system of claim 16,wherein the existing supplier has already been onboarded during asupplier onboarding process in the e-procurement system.